home *** CD-ROM | disk | FTP | other *** search
- Path: news.halcyon.com!usenet
- From: Glen Parker <glenebob@halcyon.com>
- Newsgroups: comp.lang.c++
- Subject: Can't link a .lib file...
- Date: Thu, 28 Mar 1996 12:25:15 -0800
- Organization: Computer Systems Contracting
- Message-ID: <315AF5AB.7294@halcyon.com>
- NNTP-Posting-Host: blv-pm3-ip2.halcyon.com
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 2.0 (WinNT; I)
-
- To all concerned...
-
- I am trying to write a small 32 bit windows app to send mail from the command
- line using Borland C++ 4.0. No big deal, I don't think, but here is my
- problem:
-
- I get an error when I try to link MAPI32.lib, which I found in the new MS
- SDK. So I tried to use ImpLib.exe to create a different import library from
- MAPI32.lib in my system32 dir. It blows up. And it blows up trying to run
- on all the other 32-bit dlls I tried too. AND, the compiler has the same
- error linking ALL of the 32-bit import files I tried! The linker error goes
- like this:
-
- Bad object file '..\..\mstools\lib\mapi32.lib' near file offset 0.
-
- OK, what's the deal? Can't Borland's compiler link in 32-bit libraries
- generated by Microsoft? Can't ImpLib.exe generate import files for 32-bit
- DLL's? Do I need a new version of ImpLib? I can't find one. Wouldn't you
- think that ImpLib.exe would be a freeby from Borland (like anything is
- free from Borland anymore, ha ha...)? Hmmmmmmmmmmmmmmmm... Maybe it's time
- to switch to VC++?
-
- Well, enough whining... Any insight will be appreciated, and thanx in
- advance...
-
- Glen Parker
-
-